home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19950329-19950528
/
000308_news@columbia.edu_Thu May 4 12:51:17 1995.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA29381
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Thu, 4 May 1995 08:51:32 -0400
Received: by apakabar.cc.columbia.edu id AA11179
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Thu, 4 May 1995 08:51:29 -0400
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Sudden inexplicable failure
Date: 4 May 1995 12:51:17 GMT
Organization: Columbia University
Lines: 28
Message-Id: <3oaik5$at4@apakabar.cc.columbia.edu>
References: <792124718wnr@thatches.demon.co.uk>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <792124718wnr@thatches.demon.co.uk>,
Graham Stokes <graham@thatches.demon.co.uk> wrote:
>We use Kermit all the time for occasional machine-machine transfers.
>Suddenly, after upgrading one system from SYS5R4 to 4.2 Kermit has
>developed an unhealthy attitude. It starts a transfer fine, but
>invariably enters a retry phase which terminates with the message "Too
>many NAKs". Every time, even with small files and small packet sizes.
>I've recompiled it of course, and also tried different physical ports
>at both ends. Same thing. Every time.
>
In general, it is always a good idea to recompile your non-vendor-
supplied applications (the ones for which you have source code) when
installing a new OS release. You can't expect software to keep working
when the world changes out from underneath it. If you do, and you are
disappointed, then it's the OS vendor's responsibility, not the
application's.
For Kermit, you might need a different makefile entry. If you had been
more specific about your exact platform, I might have been able to be
more specific about which makefile entry to use. But it's not hard to
locate it yourself. Just read the comments at the top of the makefile.
And make sure you have the latest release, which is 5A(190).
If you still have problems after doing that, send email direct to
kermit@columbia.edu with the detailed specifics.
- Frank